Skip to content

CNV-83484: Remove custom ConfigMap config from vgpuDeviceManager examples - #118671

Open
abrennan89 wants to merge 1 commit into
openshift:mainfrom
abrennan89:CNV-83484
Open

CNV-83484: Remove custom ConfigMap config from vgpuDeviceManager examples#118671
abrennan89 wants to merge 1 commit into
openshift:mainfrom
abrennan89:CNV-83484

Conversation

@abrennan89

@abrennan89 abrennan89 commented Aug 21, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Jira: https://redhat.atlassian.net/browse/CNV-83484

Preview link: TBA

Versions: 4.21+ (confirm)

Summary

  • Removes the custom ConfigMap config block from vgpuDeviceManager in two GPU operator YAML examples (about-using-gpu-operator.adoc and rdma-configuring-the-gpu-operator.adoc).
  • The examples referenced a custom ConfigMap (vgpu-devices-config) that users were never told how to create, causing the NVIDIA GPU Operator to skip ConfigMap creation and leaving vGPU non-functional.
  • Letting the operator manage the ConfigMap automatically is the correct default behavior.

🤖 Generated with Claude Code

@abrennan89 @claude
CNV-83484: Remove custom ConfigMap config from vgpuDeviceManager exam…
33ce618 
…ples

The vgpuDeviceManager config block referenced a custom ConfigMap that
users were never told how to create, causing the NVIDIA GPU Operator to
skip ConfigMap creation and leaving vGPU non-functional. Removing the
config block lets the operator manage the ConfigMap automatically.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 21, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 21, 2026 •
edited by openshift-ci Bot
Loading

Copy link
Copy Markdown

@abrennan89: This pull request references CNV-83484 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "5.1.0" version, but no target version was set.

Details

In response to this:

Summary

  • Removes the custom ConfigMap config block from vgpuDeviceManager in two GPU operator YAML examples (about-using-gpu-operator.adoc and rdma-configuring-the-gpu-operator.adoc).
  • The examples referenced a custom ConfigMap (vgpu-devices-config) that users were never told how to create, causing the NVIDIA GPU Operator to skip ConfigMap creation and leaving vGPU non-functional.
  • Letting the operator manage the ConfigMap automatically is the correct default behavior.

Test plan

  • Verify the YAML examples in the rendered docs are valid and complete
  • Confirm the vgpuDeviceManager section now shows only enabled: true without the config block

🤖 Generated with Claude Code

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Aug 21, 2026
@ocpdocs-previewbot

ocpdocs-previewbot commented Aug 21, 2026

Copy link
Copy Markdown

🤖 Fri Aug 21 16:24:35 - Prow CI generated the docs preview:

https://118671--ocpdocs-pr.netlify.app/openshift-enterprise/latest/hardware_accelerators/rdma-remote-direct-memory-access.html
https://118671--ocpdocs-pr.netlify.app/openshift-enterprise/latest/virt/managing_vms/advanced_vm_management/virt-configuring-virtual-gpus.html

@openshift-ci

openshift-ci Bot commented Aug 21, 2026

Copy link
Copy Markdown

@abrennan89: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@abrennan89 abrennan89 added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 21, 2026
@abrennan89 abrennan89 added this to the Continuous Release milestone Aug 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Milestone

Continuous Release

Development

Successfully merging this pull request may close these issues.

3 participants

@abrennan89 @openshift-ci-robot @ocpdocs-previewbot